The refactoring work began with editing old code for browser alerts to be changed to calling a new oo-ified alert module for the platform to allow for cleaner code. This gave me a better understanding of the codebase as a whole by sifting through each file and searching for different alert scenarios.

From then on I worked on more complex bug-fixing tasks and module development where I first started interacting with students to understand why they wanted certain changes.

I developed a new house-points display system for students and faculty to check how their intermural competitions were going.

The House Points module for the repository needed refactoring into a sleek table design, which was done with simple CSS and Javascript along with more optimised SQL queries for the MySQL backend.

The Library catalogue module required further optimisation of SQL queries to allow for better filtering of library entries, while parsing and paginating thousands of library items.

Communicating with the end users enables a developer to implement a detailed and tailored scope for software, creating something that is truly useful for the average user.

DRY and clean code is of utmost importance when working with huge object-oriented codebases to allow for the best developer experience possible for your co-workers.